Can the 'reimbursements:read' and 'spend_requests:read' Scopes Be Added to the Shared Clients' Scope Sets on Pipedream Connect to Solve the DEVELOPER_7100 Error?

Bugs
1

This topic was automatically generated from Slack. You can find the original thread here.

Hi, we use Pipedream Connect with the ramp and ramp_sandbox apps. The shared OAuth clients currently don’t request Ramp’s reimbursements:read (or spend_requests:read) scope, so reimbursement endpoints return DEVELOPER_7100 through the Connect Proxy. Could these read scopes be added to the shared clients’ scope sets? Our use is read-only (listing reimbursements pending approval). Can share error ids if useful.

2

Thanks for raising this, we’ll have a look at the app’s scopes when possible to understand if these can be added

3

do you have an ETA for this? Ramp isn’t usable as a connector on PD without it

4

No ETA yet but it is on our team’s radar.

If you can open a support ticket for this request at pipedream.com/support that would be helpful and will allow us to better track your request and keep you updated on it.